Open
Conversation
bgavrilMS
reviewed
Feb 20, 2026
bgavrilMS
reviewed
Feb 20, 2026
bgavrilMS
reviewed
Feb 23, 2026
bgavrilMS
reviewed
Feb 23, 2026
bgavrilMS
reviewed
Feb 23, 2026
bgavrilMS
reviewed
Feb 25, 2026
bgavrilMS
reviewed
Feb 25, 2026
bgavrilMS
reviewed
Feb 25, 2026
bgavrilMS
reviewed
Feb 25, 2026
Co-authored-by: Bogdan Gavril <bogavril@microsoft.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add
fmi_pathparameter toacquire_token_for_clientAdds Federated Managed Identity (FMI) support to
ConfidentialClientApplication.acquire_token_for_client(), consistent withWithFMIPath()in MSAL Go and.WithFmiPath()in MSAL .NET.Usage
What is included
New optional FMI path parameter on the client credential method — sends the path in the token request body and validates it is a string
Cache key extensibility — tokens acquired with different FMI paths are cached separately using a SHA-256 hash, with the "atext" credential type to match Go and .NET cache key format
Cache isolation — FMI-cached tokens do not interfere with regular client credential calls or with each other
Standard field exclusion — all standard OAuth2 body parameters are excluded from the cache key hash so only non-standard fields like the FMI path differentiate cache entries
Cross-MSAL compatibility — the hash algorithm produces identical output to MSAL Go and MSAL .NET, verified against their test vectors
E2E test
Added E2E test to msid client